Skip to content

Add analytics status controls - #276

Merged
baixiangcpp merged 1 commit into
mainfrom
fix/analytics-status-controls-258
Jun 26, 2026
Merged

Add analytics status controls#276
baixiangcpp merged 1 commit into
mainfrom
fix/analytics-status-controls-258

Conversation

@baixiangcpp

Copy link
Copy Markdown
Owner

Summary

  • Add visible analytics status and opt-out controls to Local Data Controls on the Privacy page.
  • Keep analytics disabled by default while storing a browser-local opt-out preference for future provider-enabled deployments.
  • Document allowed analytics events, allowed coarse fields, and forbidden sensitive fields directly in UI.
  • Add unit and component coverage for analytics preference behavior and visible controls.

Validation

  • npm test -- tests/unit/analytics-utils.test.ts tests/component/privacy-page.test.tsx tests/guards/analytics-taxonomy.test.ts tests/component/representative-a11y-axe.test.tsx
  • npm run check:i18n
  • npm run check:i18n-qa
  • npm run check:types
  • npm run check:analytics-taxonomy
  • npm run check:sitemap-lastmod
  • npm run lint (passes with existing coverage/block-navigation.js warning)

Closes #258

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying byteflow with  Cloudflare Pages  Cloudflare Pages

Latest commit: 41e6ee1
Status: ✅  Deploy successful!
Preview URL: https://b050df11.byteflow-c58.pages.dev
Branch Preview URL: https://fix-analytics-status-control.byteflow-c58.pages.dev

View logs

@baixiangcpp
baixiangcpp merged commit 3f6ddd4 into main Jun 26, 2026
2 checks passed
@baixiangcpp
baixiangcpp deleted the fix/analytics-status-controls-258 branch June 26, 2026 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Audit 21/32][P2][Privacy] Add explicit Analytics status and opt-in/opt-out controls

1 participant